Skip to content

Fix the return value in case of a parse error#233

Merged
robocoder merged 1 commit intoleafo:masterfrom
bgarret:patch-1
Jan 27, 2015
Merged

Fix the return value in case of a parse error#233
robocoder merged 1 commit intoleafo:masterfrom
bgarret:patch-1

Conversation

@bgarret
Copy link
Contributor

@bgarret bgarret commented Jan 26, 2015

Without the return, the server renders a 304 Not Modified if there's an error

@robocoder
Copy link
Collaborator

Could you instead move the return out of the try block?

Without the return, the server renders a 304 Not Modified if there's an error
@bgarret
Copy link
Contributor Author

bgarret commented Jan 26, 2015

You're right, it's cleaner this way. The change is done, let me know if you need anything else.

robocoder added a commit that referenced this pull request Jan 27, 2015
Fix the return value in case of a parse error
@robocoder robocoder merged commit cc3e894 into leafo:master Jan 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants